Clear benefit: you have Java at your disposal, while being "new and cool." From a library standpoint it is Java + extras.
Functional does not make it better: if there are two types of people, one that prefers functional, one imperative, go ahead! Let the functional use clj, the imperative use java. Now you can compile to .class and use either paradigm!
I don't code lisp regularly, but I'm convinced clojure is the NBT and so I'm preparing to jump ship after it matures :D
(It's new!)
I'm not sure how Clojure will play out but remember it's only a few years old. You could have said the same thing about Ruby in 1997.
There are similar arguments aginst Python, but less so.
As far as strong benefits of clojure: concurrency, it's lisp, it has libraries, it interoperates with Java.
Ruby is a good language, but it only became popular when it offered a clear benefit.
For a language to enter the mainstream and stay in the mainstream, it has to do a lot more than just not be bad. It has to be better than others in some way.
(By the way, being a functional language does not make it better, it makes it worse, since most programmers have trouble grasping functional concepts)
At the moment, clojure may not have any negatives, but it does not have any strong positives, so I don't see why it would catch on.