Based on my experiences hacking JBOSS, Seam, JSF2, and EJB3.. There are 2 items I would try first.
1 - Change someDao to public:
protected SomeDAO someDao; -- > public SomeDAO someDao;
2 - Add Setters & Getters to someDao object.
Hope that helps...
Unfortunately no help with that. I wonder how JSF2 is connected to EJB3 bindings?
I found this guide: http://aaron.ajexperience.com/2010/10/11/jboss-5-with-jsf-2-on-a-per-app-basis/
Could you check whether you performed those steps, too (e.g. the "jboss-mc-int-servlet.jar" part)?
How is the "architecture" of your app? Do you deploy an EAR file with EJB jar and web WAR? If yes I would guess that your "@EJB" annotation should not need any attributes at all.
As you can check from my code snippets, I was followed this manual step-by-step, and I have no problem with JSF2, but with EJB3 injection: application deploys and runs without any problem at all, but beans are nulls.
I have EAR with separate WAR for web and JAR for EJBs.