Controller initialised after a $state.go with {notify: false}

## The Bug

When a `$state.go` is called with `{notify: false}` as follows, a bug occurred:

``` javascript
$state.co('foo', {}, {notify: false})
```

On the **next state change**, the current controller will be initialised a second time.
## Plunker Link

Follow the steps to reproduce on Plunker:

http://plnkr.co/edit/wMiVOb?p=preview
