Hello Caleb Tucker,
We are sorry for the inconvenience. This is a known issue in the LINQ implementation which was fixed. The fix will be part of the next release, which will be available in few weeks.
In fact there is a workaround which you can use. You should place the where clause after the first join:
var addresses = from p
scope.Extent<CorePersonAddress>() on p.PersonId equals pa.PersonId
where p.PersonId == 1
scope.Extent<CoreAddress>() on pa.AddressId equals a.AddressId
I think that will help you.
the Telerik team