You can intercept the setSessionContext(SessionContext) method to temporarily store the sessioncontext in some singleton (like JBoss Cache).
Retrieve this context in subsequent interceptions to other method calls and at that point you can attempt to retrieve the principal details. Note if you do'nt create a login context before invoking the session bean you will not have a valid principal and it may even throw some illegal argument exception.

Hope this helps.