If it's not associated to any session object, I can't see why the container would call it. I persist to say that it's no use to register it, and that it won't be called
The API also states that
a container that migrates session between VMs or persists sessions is required to notify all attributes bound to sessions implementing HttpSessionActivationListener.. I'd like to try it though.