Why does the login exception set by the login module fail to get propagated to the caller by EJB3AuthenticationInterceptorv2?

Issue

• Why does the login exception set by the login module fail to get propagated to the caller by EJB3AuthenticationInterceptorv2?
• In JBoss EAP 4.3.0 the interceptor used was the EJBAuthenticationInterceptor. This interceptor throws the Login Exception set by the Login Module. In JBoss EAP 5.1.0, the EJBAuthenticationInterceptor is replaced with EJB3AuthenticationInterceptorv2 which does not throw the login exception back to the client. The EJB3AuthenticationInterceptorv2 currently just throws an EJBAccessException with a Message Invalid User. The actual LoginException set by the LoginModule is completely lost. The caller does not have any information on what the actual exception was.