translate5 sends unescaped xml special char via InstantTranslate to t5memory

If I translate the following sentence from de to en in InstantTranslate at a client:
Please note, I will be arriving with my family (Max Müller & Manuel Müller) a week early and will be vacationing in Singapore or Malaysia the week before.

then t5memory throws an error
E0318 18:07:13.069651 9 OTMTMXIE.cpp:3234] , with body =
"

{     "sourceLang": "de-DE",     "targetLang": "en-US",     "source": "Please note, I will be arriving with my family (Max Müller & Manuel Müller) a week early and will be vacationing in Singapore or Malaysia the week before.",     "documentName": "source",     "markupTable": "OTMXUXLF",     "context": null }

"
    lb:

{ Error during FUZZY request, id = 40867 , for memory "TM1121-ID113-XXX_TM_DE_EN"}

::[T5ERROR]::fatalError: Fatal Error: expected entity name for reference at column 74 in line 1
E0318 18:07:13.069753 9 OTMTMXIE.cpp:1777] ::[T5ERROR]::parseSrc: :: error during parsing req : Fatal Error: expected entity name for reference at column 74 in line 1

The error in t5memory is thrown because of the "&".

In my opinion, however, this should not arrive in t5memory at all, but as & - i.e. as valid xml.

This also works in the editor (just tested). But not in InstantTranslate.

So this should be done the right way for all xml special chars.