The issue turned out to be a bug introduced in Lightstreamer Server 4.0.
We have already fixed it and made available a patch a few weeks ago;
you may have received our alert through our newsletter.

Version 4.0.1 currently available on our download page is then fixed.
We apologize for the hassle.