Checklist

• I've looked at the documentation to make sure the behavior isn't documented and expected.
• I'm sure this is an issue with Leaflet, not with my app or other dependencies (Angular, Cordova, React, etc.).
• I've searched through the current issues to make sure this hasn't been reported yet.
• I agree to follow the Code of Conduct that this project adheres to.

Steps to reproduce

Go to the constructor of Map and find:

DomEvent.on(this._proxy, 'transitionend', this._catchTransitionEnd, this);

There is no removal of the event listener in the teardown code for Map, which means that creating/tearing down maps repeatedly will leak memory over time.

Expected behavior

Map.remove() should contain the following:

DomEvent.off(this._proxy, 'transitionend', this._catchTransitionEnd, this);

Alternatively, it could be done in an 'unload' event listener.

Current behavior

Memory leak.

Minimal example reproducing the issue

No response

Environment

• Leaflet version: 1.9.2
• Browser (with version): any
• OS/Platform (with version): M1 Max Macbook Pro