I can't update the affects versions but attached is a simple test case that seems to indicate this issue still exists in 5.0.6.Final