Well, I used "erase" since this is an available feature in current versions, but do you see my point? It's about separation of concerns. People who install and maintain servers (and some of our customers have this even outsourced, so our application runs in a shared server along with other applications) are different from the people who design applications. Maintainers should not have to read pages of instructions filled with internal details for all of their deployed applications. They certainly do not want to modify the server anytime a new application or version must be deployed. They must have generic knowledge about pools sizes, memories, muticast etc., anything application specific is not their concern and should therefor, if ever possible, be provided within the deployment unit. I think if you already have a management API for java clients, building a deployer around it to add resources to a subsystem isn't that hard anymore (but I dont know the internals) and would be worth the work.
I really look forward to AS 7 and been playing around with it since the first alpha. But if deployables queues, datasources or jaas-application-policies are left out, it would change our picture damatically too...