I don't agree with everything suggested here, but this is similar to what I'm talking about
http://www.lihaoyi.com/post/StrategicScalaStylePrincipleofLe...
especially the reasoning that you should try to avoid mutability, but when something is mutable, just make it mutable. This is much more in line with ML approach than with typical Haskell concerns around effects systems.
ML on the JVM seems like a nice niche for it, but I'm not sure I really have seen libraries or Scala devs sorta advertise their style/library as ML inspired. I've seen OCaml mentioned as an inspiration to Scala before, but there are some notable differences between the two (e.g. inheritance vs structural typing)