Are feature start levels used when installing features in a fabric container?

Issue

• Are feature start levels used when installing features in a fabric container?

• In a standalone container how to specify a bundle start level using "features.xml" file, is this property honored when installing features in the Fabric container?

• We are creating child standalone container in fuse like below

jboss-fuse-redhat/bin/admin create -f

• I would like to know how to add all features available at root container to child container by default. I do not want to manually specify all feature names while creating the child container.
  Please please let me know if there there is any way to make all features available to child container

• Due to a memory leak within fuse when regularly connecting to the fuse console using ssh, we restart regularly our fuse servers. Now we have problems with our ActiveMQ server.

  Since our applications do not share state we have a setup of two fuse instances which share a common activemq database as described in the A-MQ documentation "Fault tolerant
  messaging" as "Master/Slave with shared file system" using nfs as shared file system.
  I assume the our problem comes from not shutting down the application properly, since the active mq component and our application components share the same startlevel 60.
  So now my questions:Is the startlevel also used for shutdown ?