I have just validated this bug posted on Connect. It seems a compiler issue, I'd like to read a Microsoft answer about this.
However, the general issue is that using ArrayList in a lambda expression with a collection initializer could be dangerous. There are not so many reasons to use an ArrayList in a lambda expression, unless you are refactoring or working with legacy code that cannot be modified upgrading ArrayList to generic collections.