no, in both cases you can traverse associations without any limitations. In fact AuditReader.find is just a decorator for a query.
I think the problem might be related to this:
When I start auditing Organization, the entries in the join table between Organization and Asset aren't correct. dbunit dump:
<MTE_ORGANIZATION_MTE_ASSET_AUDIT asset_id="2a6027a2-e076-4476-a05f-50e7a88e3d97" audit_revision_number="42"/> <MTE_ORGANIZATION_MTE_ASSET organization_id="35128729-c3b2-46a1-9f90-4aae1fc7ed24" asset_id="2a6027a2-e076-4476-a05f-50e7a88e3d97"/>
there is no organization_id or audit_revision_type (REVTYPE).
I closed the bug and released Envers 1.2.1 (should be up on the site soon), so check if this solves your problems.