Furthermore, Clojure can use the already existing Java libraries, while in Haskell's case, the number of available libraries is considerably smaller. Clojure plays nicely with Java, so you can mix and match Clojure developers with Java devs, and they won't go for each other's throat.
Haskell doesn't play all that well with any other language.
I also agree with Madhouse's explanation of the steeper learning curve. The biggest problem with the steep learning curve is that there are far fewer examples in the wild of solving business problems with Haskell. The library support that Madhouse mentioned also compounds this problem.
Java is everywhere, if a company is switching from java to a functional language, it's cheaper to make an organic transition using clojure, reimplementing when it seems appropriate, than it is to use Haskell, where no code could be left unchanged.
There are of course practical benefits of haskell to employers. It's faster, it tends to be easier to make major extensions to a haskell project without refactoring than in other languages, it's easier to reason about the code so new employees will be confident sooner, Haskell protects against subtle bugs that might not be noticed during debugging, etc.
Also, just because Haskell has been around longer than clojure, it was considered an exclusively academic language until only a few years before clojure came out.