No, we just changed to using Spring to inject the stuff rather than using @Resource. This worked because we were already using Spring for other things.
That being said, I haven't tried this since we switched to version 7.1.x, so it might have been fixed there, I don't know.
Sorry, wish I could be more help.
As is usually the case, 5 minutes after I make a post seeking help with a problem I discover the solution. In this case, I was trying to access the @Resource fields in the constructor. When I changed the constructor to an @PostConstruct annotated method (because I am using Stateless bean) low and behold the @Resource fields are resolved and everything works just fine.
I use a Stateless bean because that is one of the types that is scanned for @Resource annotations. I don't think a POJO, as in your example, gets scanned for @Resource annotations.