Currently Named query validation happens at first EM creation. This results in two issues.
1. Archives with invalid named queries are deployed successfully and we get a runtime exception while using them
2. If Java2db is turned on, the exception for named query validation gets the container into an inconsistent state.
This issue has been reported in various user forums and we have also observed Arun struggling with it while developing JavaOne demo.