It has meanwhile been debunked that this file tracks the location of the iPhone. It draws a map of locations of cell towers. The positions in this file are not the position of the iPhone when the user used a location app, the positions are the locations of the cell towers the iPhone saw in this moment. This is pretty clear now. The cell tower ID is the UNIQUE ID of the database, there are only clusters of tower locations saved at the same time with locations miles apart and NONE of these are the actual position of your phone.
Some real world testing:
http://www.willclarke.net/?p=247 [willclarke.net]
And yes, this also paints a rough picture of where you used location services, because only the stations around the places where you used location services are in this database. But: The stations are miles around your real position and since there is no signal strength info saved triangulation is not possible. I have found stations recorded that were up to ten miles away from my true position and hardly any stations nearer than half a mile (you'd need to stand right under a cell tower and use Google Maps there to have the position of the iPhone and the tower match by accident, so this happens almost never and the data shows exactly that).
So: The iPhone builds a local database with a network topography map and never throws it away. If it would throw that info away it would need to ask external databases (of Google or SkyHook) instead to learn the coordinates of the towers that it sees. By doing so it would neccessarily TELL these providers where it is.
Basically you have the choice of your phone tracking you (very roughly) in an internal database or have someone else providing an external database and by this tracking your phone. The iPhone does the first, Android does the latter (and Android even sends the Unique Device ID along). Believe it or not, but technically Jobs is right. The iPhone tracks you in an internal database, but with Android Google tracks your phone in external databases.
I don't expect many people to understand that though. Even with much explaining to basically neutral people hardly more than 5 of ten understand how positioning works and what it implies. Or what a "Unique Device ID" is.