The most critical scalability feature of good geospatial stores has nothing to do with indexing algorithm per se: the ability to adaptively reshard and migrate data/load between cluster nodes. Geospatial data models are inherently prone to hot spotting which becomes worse as data models grow.
Also, GeoMesa implements an 'XZ'-curve schema which gets around a few of the problems just using a Z-order curve runs into.
To the point about hot-spotting, there's a configurable sharding strategy that can help spread the data around more of the nodes in the cluster.
I haven't seen an easy/obvious way to apply adaptive quad-tries on top of key-value stores like Accumulo and HBase. Managing complex data structures in a cloud seems to be rather difficult.
Intuitively, if you look at the z-curve map below, some parts of antarctica which are adjacent, are not close on the z-curve.
http://www.geomesa.org/documentation/_images/Zcurve-HiRes.pn...