It's part of yesterday's 5.5.0.Final release. Could you give that a spin and report back whether it fixes this issue for you? If so, we can close it as out-of-date. Thanks!