Should this little jig be turned into a separate bug? Perhaps ngModelController could compare `value.length` to the old length (and try not to break in the case of scalars, of course) --- to avert this somewhat. Or perhaps just use the objectEquality flag?