I'm not sure why this has not been seen in the past, but the ResourceHandler.loadXmlResourceEnvRefs is not handling the well known TimerService type similar to a UserTransaction as it should. The result is that a simple @Resource TimerService x; reference fails with a missing mapped-name exception. Its a simple fix, just not sure how it was lost, never implemented. I'll fix it and check whether its seen in the current cts failures. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155483#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...