JWT token appears to be reused if user who is moderator, ends meeting, then joins another

When hosting a meeting on self-hosted Jitsi, the host is required to start in our app portal that provides a jwt in the url. Guests simply go to the url without a jwt. If a host ends a meeting and joins a different one as a guest, their identity is kept from the initial meeting. Should that user who was hosting a meeting, joining another meeting simply be a guest?

Is this a Jitsi issue or a browser cache issue? Are expire of the token is at about an hour. Any help would be greatly appreciated. How can we ensure that tokens aren’t being held on to after a user sets a meeting. Do we need shorter jwt life?