I'd bet that with a server JVM and hot code, there's nothing you could do to speed it up (since the JVM does all the optimizations already). Especially, myArray.length gets cached in a local variable and the loop gets unrolled several times.
In case you care about performance with a weaker JIT compiler, you could do the two above things manually, but why should you care?
A side note
Interestingly, there's a similar loop where the JVM is pretty loosy:
for (int i = 0; i < value.length; i++) {
h = 31 * h + val[i];
}
It's not an unimportant piece of code, it's the body of String.hashCode. By unrolling it manually you can get a speedup of factor 2+.