NIM055232 fixes the opposite of the issue that you are having, no matches would occur if the locator is built without all of the zone fields mapped.
There is an issue where the score is higher than expected when a locator is built with not all of the zone fields mapped. Essentially, the locator assumes that, in your case, the city and the state field have a score of 100 and the zip has a score of 0. This increases the total score of the address and therefore can be a bit confusing.
There are a couple work-arounds that we can try and use if you would like. The first would just be to increase the minimum match score to something like 96. Another option would be for me to provide an updated style for you in which you could build your locator from.
Just let me know what works best for you and sorry for the inconvenience.
Brad
The score should be lowered.
In this case I am trying to teach how to find the errors and evaluate them plus how to use the geolocator. Although I think the way the zipcode is ignored is an error. You cannot assume that the address you are trying to locate is in the range of the geolocator. For instance if you were trying to geolocate participants at a local event, you could get participants from out of state thus with a valid zipcode that should not match to your locator.