LdapUserDetails Mapper changed in Spring Security 3.0?

Question

In the earlier versions of the spring security, The LdapUserDetailsMapper used to have an attribute to store custom user attributes like samAccountName, givenName.... But with the recent release in Spring security 3.0 apparently something changed and there is no way to store these details which we can access later from security context. Is there any elegant way of handling these values instead of storing in session (Obviously we don't want to access two different session variables for getting user details). I tried overriding the LdapUserDetailsMapper and added a custom attribute to hold which required overriding the User object too, leading to extending the LdapUserDetailsImpl (to override the essence). Is there a better way of doing this?