Description of problem:
Trying to remove the config for server-one while it's still running produces an uninformative failure:

[domain@localhost:9999 /] /host=master/server-config=server-one:remove
{ "outcome" => "failed", "result" => undefined, "rolled-back" => true, "server-groups" => undefined }

An EAP 6 user reported a similar problem but with a different response:

[domain@localhost:9999 /] /host=xyz/server-config=as1:remove
{
"outcome" => "success",
"result" =>
{ "outcome" => "failed", "failure-description" => "[core-service, path, server-config, system-property, jvm, interface]", "rolled-back" => true },
"failure-description" => undefined
}


Steps to Reproduce:
1. Edit the host.xml so that all servers 'auto-start' to be 'false'.
2. Execute domain.sh. Only the process controller and the domain controller are started.
3. In the jboss-cli.sh, try to remove a server-config then you'll get the error.

[domain@localhost:9999 /] /host=master/server-config=server-three:remove
{
"outcome" => "failed",
"result" =>
{ "outcome" => "failed", "failure-description" => "[core-service, path, server-config, system-property, jvm, interface]", "rolled-back" => true },
"rolled-back" => true
}

4. If there are any running servers, the remove command succeeds as expected.

[domain@localhost:9999 /] /host=master/server-config=server-one:start
{
"outcome" => "success",
"result" => "STARTING"
}
[domain@localhost:9999 /] /host=master/server-config=server-three:remove
{
"outcome" => "success",
"result" =>
{"outcome" => "success"}
}