My reason for not using it originally was that we had prototyped our solution using Compass (which was the project before Elasticsearch) only to have it abandoned to work on Elasticsearch. So I was concerned about the "one dev" model and losing something that was a key component of what we needed.
Since then I've not been impressed with SolrCloud (would love to hear good experiences, but it seems their distributed model isn't right) and have been giving Elasticsearch serious thought again.
I didn't say nor mean to imply that. Technically, Solr is based on servlet technology whether stand-alone or not, you can choose to deploy it in a web container of your choice or use the Jetty instance it comes with for the "stand-alone" experience. I don't know much about Elasticsearch's architecture personally.
Just use a different transport implementation:
https://github.com/elasticsearch/elasticsearch-transport-war...
The documentation is also fantastic and the plugin availability pretty good.
The best proof is that Elastic Search is slowly hitting the same problem Solr hit at some point in the past and has to deal with them (scripting is now disabled by default, analysis/query language is slowly getting more complex, etc).
Not trying to downgrade ElasticSearch, they have done great things and have features Solr hasn't matched (yet). Percolation is one (though check Luwak for a comparison: http://www.berlinbuzzwords.de/session/turning-search-upside-... )