I can confirm that the issue is due to an unusual behavior introduced by Firefox 48.0 that concerns document.domain set on iframe/parent when coming from different ports.
The behavior is also explained here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1292522 .
In case of Lightstreamer client lib 5 (or lower) the only workaround viable is to uniform the port number between web and lighstreamer servers.
I also confirm that JavaScript library 6 or newer is not affected by the problem since totally different techniques are used.