Reproduced on Chrome, might happen on other browsers as well:

1. added to the async publication two sleep (30) calls, just before and after object publication, to simulate a long-publication event
2. tail -f | grep the apache access log, to see incoming requests
2. send an object to publish
3. open 2 more tabs, on the same url: ezflow_site_admin/content/queued/149/14
4. verify that 3 ajax requests per second come in
5. what happens at the end: when object was published, tabs 2 and 3 stopped polling, and showed link to published object, while tab 1 did not and kept going on

Note that I did not reproduce it, but a customer has problems where sometimes the opposite happens: a page stops polling for a time going up to 30 minutes, leading the editor to think that a page is not published when it really is