Fixed faulty loop management when unsubscribing listeners

[kytart]

There's a bug in the nested foreach loop.

It iterates over all listeners for the given event, searching for the index of the subscriber, that should be unsubscribed for this event. When the subscriber in the current iteration isn't the one we're looking for, it should continue to the next one. However there's continue(2) instead, which causes all other subscribers to be skipped and the loop continues with next event.

The result is that, if the subscriber is first in the array of subscribers for a given event, it's successfully unsubscribed as expected. If it's not the first, then it won't be unsubscribed because the whole array will be skipped.

This commit fixes the bug, changing continue(2) to continue to properly continue to another subscriber in the array.

[enumag]

Can you add a test?

[kytart]

Ok, I will later

[fprochazka]

It would be great if you could add a test case, so nobody will break it again.

[fprochazka]

I've written the test-case myself, so I could merge this. Thank you for reporting the issue and providing a fix!