SWITCH...CASE vs SELECT...ACTIVE

Today I got caught by a problem that, after some debugging, came down to this:

A 'SWITCH...CASE' does not work after a WAIT, while a 'SELECT...ACTIVE' does.

DEFINE_FUNCTION fnEndCeremony()
{
    WAIT 20
    {
    SELECT
    {
        ACTIVE (nEditorPlayerMode == PLAYERMODE):
        {
        SEND_STRING dvCMP, 'blabla_active_playermode'
        }
        ACTIVE (nEditorPlayerMode == EDITORMODE):
        {
        SEND_STRING dvCMP, 'blabla_active_editormode'
        }
    }
    SWITCH (nEditorPlayerMode)
    {
        CASE PLAYERMODE:
        {
        SEND_STRING dvCMP, 'blabla_switch_editormode'
        }
        CASE EDITORMODE:
        {
        SEND_STRING dvCMP, 'blabla_switch_playermode'
        }
    }
    }
}

If you execute the above function, the 'SELECT...ACTIVE' works fine, while the 'SWITCH...CASE' throws errrors:

Line 4 2017-07-18 (23:13:44.244):: Assign Stack Ref Error - Out of range
Line 5 2017-07-18 (23:13:44.245):: SetVariable - Error 2 Tk=0x1005
Line 6 2017-07-18 (23:13:44.247):: DoNumberExpression - Error 2 Tk=0x2008 Line=46
Line 7 2017-07-18 (23:13:44.247):: GetNumber - Error 1 Tk=0x0000
Line 8 2017-07-18 (23:13:44.250):: DoNumberExpression - Error 2 Tk=0x2008 Line=50
Line 9 2017-07-18 (23:13:44.250):: GetNumber - Error 1 Tk=0x0000

If you remove the WAIT, both options work fine. Of course this code snippet is not how it appears in the real program.

Is this expected behaviour? If so, which is 'correct'? I can't imagine that today would be the first time I used a SWITCH...CASE after a WAIT . Could it be that this has changed in a recent firmware?

I ran into this on a NX processor with the latest firmware and tested the code snippet on a NI-3100 with v4.1.419 firmware