Have you enabled the multiple-host option on the port in question? With the multiple-host option "not" enabled, when a host logs off, the server sends an EAPOL-logoff message causing the switch port to transition to the unauthorized state. Thus, when a new user logs in, the authentication process will be initiated again. My guess is that with the multiple-host option enabled, this message is being supressed since there might be other active hosts on the port, and sending the port into the unauthorized state will cut off the still-active hosts. Thus if you are not seeing the eapol logoff, you are probably seeing behaviour that is expected. Either this or you are running into some bug.