CLI shutdown * operation (kills domain controller first, beheads host controllers)

From the CLI with a domain controller and two host controllers running, using wildcard command intended to shut down everything:

[domain@localhost:9999 host] cd ..
[domain@localhost:9999 /] ls host
host2-9 host3 master
[domain@localhost:9999 /] ./host=*:shutdown

[domain@localhost:9999 /] ls
[domain@localhost:9999 /]

Success is reported, and we're no longer connected to a domain controller. A follow up check reveals that the domain controller (host=master) was shutdown, but the host controllers (host2-9 and host3) are still up and now searching for the missing domain controller:

<snippet from host3 console>
[Host Controller] 20:47:07,351 WARN [org.jboss.as.domain.controller] (Thread-14) Could not connect to remote domain controller 127.0.0.1:9999
[Host Controller] 20:47:22,357 WARN [org.jboss.as.domain.controller] (Thread-14) Could not connect to remote domain controller 127.0.0.1:9999
[Host Controller] 20:47:37,364 WARN [org.jboss.as.domain.controller] (Thread-14) Could not connect to remote domain controller 127.0.0.1:9999
[Host Controller] 20:47:52,370 WARN [org.jboss.as.domain.controller] (Thread-14) Could not connect to remote domain controller 127.0.0.1:9999

It appears that the DC was shutdown first, so no communication path the HCs, so they were not shutdown. Perhaps the wildcard should be disallowed for the shutdown operation, or intelligence added to shutdown the DC last... Just wanted to let you know.

Running something called jboss-as-7.1.0.Alpha2-SNAPSHOT downloaded by Rich Raposa for a GLS class around 10-Nov-2011. I chose "Affects Version" because that was the closest on the list...