We also ran into this problem and it seemed that this was simply hiding an exception that was occurring in the session bean. We use log4j, and so I had to go searching in the log4j logs to find the actual error message.
[Message sent by forum member 'kneecha' (kneecha)]
http://forums.java.net/jive/thread.jspa?messageID=307762