Possible memory-leak through QCocoaEventDispatcherPrivate::temporarilyStopModalSession

The CCocoaEventDispatcher keeps a list of currently active sessions via cocoaModalSessionStack. This stucture connects (amoung other) an NSWindow * (QCocoaModalSessionInfo.nswindow) with an NSModalSession * (QCocoaModalSessionInfo.session).
When a session is created the corresponding nswindow is retained (see

{QCocoaEventDispatcherPrivate::currentModalSession()}

) and latter (when the sessions are finally destroyed) retained (see

{QCocoaEventDispatcherPrivate::cleanupModalSession()}

).
However, is is possible to "temporarily" destroy all modal session via QCocoaEventDispatcherPrivate::temporarilyStopModalSession() let them recreate via

{QCocoaEventDispatcherPrivate::currentModalSession()}

. In this case an additional retain-call is executed on the nswindow, which is not outbalanced by an release-call.
Except i miss something.