updating getFeatures so that rather than temporarily removing each layer in order to query the layers underneath, each layer is temporarily elevated in turn (thorugh its zindexing) so that each layer can be queried as if it were on top.  this addresses the problem in which other controls (namely utfgrid control and the click event in my case) were not always being triggered when vector layers were on the screen.  my suspicion is that the temporary removing of layers by getFeatures was disrupting these other events.  NoTE:  this change also removes a section of code in getFeatures, one that had utilized a similar (display = none) strategy, to identify all features under a mouse event in each single layer.  I don't have a solution for accurately querying such layers that have overlapping vector features, while allowing for the possibility of other controls and event triggering. Although one might involve the temporarily enabling zIndexing for a vector layer so that the zindex of each feature in the layer can be temporarily adjusted/elevated...?