As a followup for those who are interested, I opened a case on this and their response at this point is that the reservations information comes from two places, the vRA (postgres) database and IaaS database. When they perform the rename the objects seems to be updating in vRA, but only in IaaS when these are created initially (i.e removing and adding back).
I am not sure at this point if they will fix this behavior since going forward this should not be an issue, as in vRA 8.x it does not use the IaaS model.
If anyone wants to chime in to GSS about it and try to convince them to fix it, that would be appreciated.