Map fails with small number of results from Views

G'Day,
We're having trouble with the display of a Views-driven map with a linked Views table display. The number of features is apparently causing something to fail with the map rendering.
I'm not sure where to troubleshoot, but can give some examples to show why I think it is the total weight of the returned features that causes the issue.

The map is here:
http://directory.communitygarden.org.au/directory/explore

(1) A query that returns only 4 features can be seen by entering "NT" in the State field. Map displays fine.

(2) A query that returns 11 features can be seen by entering "SA" in the State field
Returning 11 features causes the View to be shown using a pager, and again it displays fine, although the map display does not follow the returned results (note that all 11 features are shown on both pager pages)

(3) However, when we get to 19 results (again this is only two pages, as above), the map display fails and returns a "tiled" version of the globe. This result can be seen by entering "QLD" as the State term.

I can reduce the number of fields being returned by Views (we have about 20 fields currently) in the hopes of extending the "envelope" of how many features can be returned. I can't imagine that deleting a few fields is going to improve the map results very much, and the more popular states have over 200 listings.

So ideally:
(A) we would find a way to get the map to follow the pager of the tabular Views display, AND
(B) we could find out why the map chokes with this little bit of feature load.

Any ideas for how we might proceed?