Are you using hotdeploy? I've seen this happen when you hotdeploy a session-based
component but have an old instance of the class in the session.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124984#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...