<isd>
xhr is just the browser API for making HTTP requests. So it seems like there's a meteor issue (possibly an issue in one of the underlying libraries) where stuff falls over if there are too many requests.
<isd>
So it has nothing to do with websockets per se.
<isd>
(I should say, the old browser API; fetch is much nicer to work with)