I don't recall if it was officially confirmed that this would be fixed in the next patch, but it is a known issue (not sure if it was known before the US 1.03 release).