Just patched JBoss 4.0.4-GA to EJB3 RC9. With no code changes, redeployed my existing archives and have received deployment errors related to @EJB injections not populating instance variables as they once were. EJB A depends on EJB B (@Depends). EJB B is successfully deployed before EJB A, and appears in both JMX Console and JNDIView. EJB A also injects an instance of EJB B. This instance remains null in EJB A's JMX "start" method. Both EJBs are JBoss JMX @Service Beans. Anyone else seen this? S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972664#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...