The critical infrastructure pieces (where GC is an issue) are already in C++. The front-end is already in Java. A full scale re-write will be a dumb thing to do. It's not going to be difficult to have Common Lisp FFI to hook the ITA middleware into Google's infrastructure instead of ITA's.
The software that ITA developers that makes them different from the rest (I am guessing lots of these are heuristic solutions to NP complete problems) is exactly the sweet spot for Common Lisp, where it provides a significant advantage over other languages even for large groups of programmers. While I will enjoy writing a web app in Common Lisp much more so than writing a web app in Java (less boiler plate, interesting language compensates for a mundane task) I doubt there are going to be great advantages to doing the more routine development in CL for a large corporation.
Classic paper by Carl de Marcken, co-founder and former CTO of ITA Software, elaborating the unique domain problems of air travel planning:
"Computational Complexity of Air Travel Planning"
http://www.demarcken.org/carl/papers/ITA-software-travel-com...
When did this happen? From what I heard last, C++ was just the data importer that dumped everything into mmapped buffers which SBCL worked on.
I didn't mean critical computation, query and logic components. Perhaps "infrastructure" was too vague.
See http://danweinreb.org/blog/the-failure-of-lisp-a-reply-to-br...