Why fight it and not simply have the MDB shim for a real singleton that you do have control over? There's nothing in the spec guaranteeing an MDB having an infinite lifespan, so you can't rely on it anyway.
Have the MDB call methods of a @Singleton Session Bean. Then you get all of the promises of the container.
[Message sent by forum member 'whartung']
http://forums.java.net/jive/thread.jspa?messageID=479728