This is likely due to the same Cloud Push being sent for each push ID.

Sending icepush-ee/core/src/main/java/org/icepush/BlockingConnectionServer.java
Sending icepush-ee/core/src/main/java/org/icepush/LocalPushGroupManager.java
Transmitting file data ..
Committed revision 36356.

When reloading the page a new PushID is created, and the old PushID(s) are still part of the listen.icepush requests. In addition all PushIDs are still part of the same Group. Due to the lack of a BrowserID class representation at the server side at the moment, a ConfirmationTimeout TimerTask was being scheduled for every PushID in the Group, regardless of if multiple PushIDs belong to the same BrowserID. There can be up to a single NotifyBackURI per BrowserID. Each PushID can have up to a single associated NotifyBackURI. When iterating over the PushIDs of a Group it will keep track of if a particular NotifyBackURI already has its ConfirmationTimeout TimerTask scheduled. If not, schedule it, otherwise skip it. Marking this one as FIXED.