Current implementation of GlassFish 3.1 has few mbeans being created by web container.
These Tomcat mbeans are loaded at startup and not lazily loaded.
All other GlassFish mbeans are loaded only on the bootAMX() call, which happens after the startup upon first access at the JMX port.
1) All mbeans should be loaded lazily (on first access)
2) We should have one set of JSR 77 mbeans
After a conversation between Dhiru, Amy, Prasad and Nazrul, we decided the following...
1) Since this is late in 3.1, we will leave the tomcat created mbeans under "glassfish-web:". We will try to comment out (not create) mbeans that are not needed by web container initialization.
2) During 3.2, we will try to not rely on mbeans for web container configuration update notification. Instead, we will rely on HK2/config layer from GlassFish and not create these mbeans any more.