Incorrect behavior of resource-adapters subsystem configuration

There are problems:
1) to remove resource-adapter resource from configuration you need to execute "remove" operation twice:
[standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=some:add

{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=some:read-resource(recursive=true)
{
"outcome" => "success",
"result" => { "admin-objects" => undefined, "config-properties" => undefined, "connection-definitions" => undefined }
}
[standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=some:remove
{
"outcome" => "failed",
"failure-description" => "JBAS014762: Removing services has lead to unsatisfied dependencies:
Service jboss.resourceadapters was depended upon by service jboss.resourceadapters.ra.some",
"rolled-back" => true
}
[standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=some:remove{"outcome" => "success"}

[standalone@localhost:9999 /]

2)it isn't able to parse <admin-object> in resource-adapter configuration, if there isn't <config-property> element, so this configuration doesn't work
<admin-objects>
<admin-object
class-name="Class3"
jndi-name="java:jboss/Name3"
pool-name="Pool2"
use-java-context="false"
enabled="true">

</admin-object>
</admin-objects>