JBossMappingManager uses incorrect (misleading) Logger

While debugging an issue (through logs), I realized after much fighting, that JBossMappingManager uses an incorrect logger:

public class JBossMappingManager implements MappingManager
{
protected static final Logger log = Logger.getLogger(JBossSecurityContext.class);

Notice that it's using the JBossSecurityContext.class as the logger name.