The scope of the bug is to ship (to Beehive users) a standalone controls test environment that can be used to host arbitrary controls testing. The classes currently being used in the EJB, JMS, and web service controls aren't sufficient to meet these needs (IMHO) as they don't provide the flexibility that's needed by the test author to subclass / delegate, extend the container context, etc.
IMHO, until the feature set is delivered, this bug needs to remain open as the goal (delivering this to users) hasn't quite been met yet.
Unfortunately, this won't make it into Beehive 1.0 as I've not had enough time yet to port some of the controls tests to use the new container and thus it's not entirely validated yet...
Should happen right after we ship Beehive 1.0.