Hi Arx,
Did you file this specifically on 5.0.z because it's the only release it was encountered on? Just wondering if you were able to re-produce on a later release? It is going to be hard to justify pushing an async update for this at this point without a customer case, but we should ensure it is fixed on later releases.
Thanks,
Steve