I think the situation now is far better, otherwise we wouldn’t became aware that something is off. As client library developer I’m deeply thankful that the issue was pointed out, which very likely wouldn’t be case if the server would simply ignore inconsistent response.
Also the user can simply turn off stream management to avoid the issue. Turning off stream management in such a case doesn’t mean much service degradation, because the stream management implementation is probably unreliable anyway.