Depending on how the application uses ace:gMap and its subcomponents, it is possible to register the same event multiple times after dynamic updates.

Here are two specific scenarios:
* Whenever an ace:gMapEvent is rendered, it will cause an update, simply because the script contains the hash code of the object. The dom-diff detects this as an update and sends the new markup to the client, which registers the same event again. To fix this, it will be necessary to remove the hash code from the markup and also to keep track of the different events by id, in order to avoid registering them again.
* With ace:gMapInfoWindow, the client-side code does an initial check to see if the window exists, and if it does, then it is closed, but the script continues setting up all the listeners, and if 'showOnClick' is true, then the parent marker will get registered an additional event listener to open the info window on click, causing multiple instances of the same window to be opened, stacke don top of each other.

There might be other similar situations throughout the code, where events are registered multiple times. So, it will be necessary to examine the entire code to look for this kind of situations.