Selected features with a join are identified improperly from a service

We couldn’t figure out why a service fails to provide correct identification for the selected feature. However, the scenarios below may highlight the issue:

1. In the “UrbanMasterPlans_WithJoin.mxd” file, the attribute table of the “UrbanMasterPlans_PNA_Approved” layer is joined with the “Regulations” table, then the ArcGIS Server fails to identify all the selected features.

2. In the “UrbanMasterPlans_WithoutJoin.mxd” file, the attribute table of the “UrbanMasterPlans_PNA_Approved” layer is not joined with the “Regulations” table, then the ArcGIS Server is able to identify all the selected features.

Here is data link to test the problem: http://www.mediafire.com/download/ev5wthdiijhp51n/PublishingIssue.zip

What might be the issue here? Why does the join affect the Identify results when applied in a service?