On both accounts, the short answer is: that's entirely up to you. If both web modules, the application, and the MDB are deployed in the same JVM, that should make things easier for you; you'd be able to make a central registration point (probably backed by a Map so you can do key-based lookups) to hold the SFSB stubs such that they could be obtained from either webapp (remember, only one can have access to any one stub at a time). As for the MDB listener - I haven't seen the size of this SFSB, but if its small enough you could probably send it as a field of a POJO in an ObjectMessage. Or have the MDB do the lookup just as the webapps are through the centralization. Again, I don't have your specs...the above are simply some ideas that jumped out at me without fully analyzing your particular problem. And of course, be sure to call your @Remove method on the SFSB when you're done with it. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088193#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...