Actually, I think this has slipped through the cracks since the client releases were separated out from the main View infrastructure releases. Typically virtual hardware support has lagged a little, e.g. with 5.0 it didn't support HWv8 to begin with: VMware View 5.0 Documentation Center
I suspect what happened is that because View infrastructure moved forward but there wasn't a matching client released as part of it, there was nothing to track the limitation. It should have been included when support for vSphere 5.5 was announced in the release notes. I raised an internal note to track this for the next 5.3.x server release.