Want to address a future feature and get a feel for how much work would be required. We've currently got @Service, which deploys a Singleton EJB and exposes a JMX View. Oftentimes this is used strictly to get a hook into a Lifecycle (ie. "I want a callback for when my JAR is deployed"). And JMX exposure is not necessarily desired. I'd like to introduce the notion of an MC EJB, which would have the following features: * Full EJB (Tx, Security, etc) * @Singleton (Same model following EJB3.1 with regards to concurrency) * POJO w/ annotations to denote Callbacks (@Service requires Management interface) * Proxy is installed into MC and therefore becomes a valid MC Bean; though when MC POJOs invoke on the EJB MC Bean, a typical EJB call starts. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153826#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...