I'm using a custom loginmodule which accesses a secured bean "SecurityBean". I'm using module-stacking with the RunAsLoginModule to gain access to the secured bean.
The bean again accesses another beans "WorkflowBean" to collect userdata. With JBoss 4.3 everything was working fine. Now with JBoss 5.0, the behaviour is like this:

• The loginmodule successfully accesses the SecurityBean
• When the SecurityBean accesses the WorkflowBean, the interceptor kicks in and forces another authentication with the loginmodule.
  This leads to an endless recursion. Both beans have the same securitycontext.