I've identified this and we'll get this fixed in the next maintenance release (shipping end of week, at the latest) as BM-3552