Problem is that it is almost impossible to decide whether interning makes sense. About the only way I know is that, if you run out of memory and use a lot of strings, you can think “let’s give interning a try”.
Even if you know the answer, you cannot tell libraries you use to intern strings they create. So, if your libraries create lots of long-lived strings, you do not have control over whether they intern strings.
Also, if you do write a library, the call whether to intern or not to intern is impossible to make because you cannot know whether your callers prefer speed or memory usage, and whether the objects you return to them will be long-lived.
For example, if you write a XML parser library, interning tag names may be the best guess, but libraries that do not do that may beat you in short benchmarks.
Because of that, I think it would be more useful to either have some way to globally install a ‘should I intern this string?’ handler (but what kind of information should that get, so that it can make an informed decision?), or to have the garbage collector intern strings as it sees fit. Problem with that is that it can change the behaviour of programs that compare strings using ‘are the same object’ comparisons. Maybe that feature should be removed from your language.
Also note that modern Java allows one to tweak its interning behaviour a bit (http://java-performance.info/string-intern-in-java-6-7-8/)