Hi Tino,
I see the fix made it into 16.1 under another CR number (xos0060179). That explains why you see it working there.
Also, I noticed an update to the CR Andrew mentioned (xos0061283) - The fix is now expected be included in 15.7.2.
Yes, the behavior thus far in our testing indicates the unexpected behavior is particular to EXOS 15.7. CR xos0061283 has been assigned to the issue. The software fix is currently scoped for EXOS 15.7.3.