Improper error handling when attempting to remove a server-config with a running server

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
}