disableHTTPRoute = true in runtime does not clean CR.status.hosts

Reproducer:

1. create CR

   apiVersion: wildfly.org/v1alpha1
   kind: WildFlyServer
   metadata:
     generation: 1
     name: eap-cd
     namespace: default
   spec:
     applicationImage: >-
       brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4
     size: 1
     disableHTTPRoute: false
   

2. Edit CR with disableHTTPRoute: true. I would expect Route object will be deleted.

   apiVersion: wildfly.org/v1alpha1
   kind: WildFlyServer
   metadata:
     generation: 1
     name: eap-cd
     namespace: default
   spec:
     applicationImage: >-
       brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4
     size: 1
     disableHTTPRoute: true
   

3. Route object eap-cd is not deleted but status.hosts is still filled

   apiVersion: wildfly.org/v1alpha1
   kind: WildFlyServer
   metadata:   creationTimestamp: '2019-10-01T17:20:34Z'
     generation: 2
     name: eap-cd
     namespace: mchoma
     resourceVersion: '629943'
     selfLink: /apis/wildfly.org/v1alpha1/namespaces/mchoma/wildflyservers/eap-cd
     uid: c7535f3f-e46f-11e9-b4ad-02e6008f3048
   spec:   applicationImage: >-
       image-registry.openshift-image-registry.svc:5000/eapcd-suite-builds/eap-cd-openshift-rhel8:17.0-4
     disableHTTPRoute: false
     env: []
     envFrom: []
     replicas: 1
   status:   hosts:     - >-
         eap-cd-route-mchoma.apps.eap-qe-cluster105.eap-qe-cluster105.fw.rhcloud.com
     pods:     - name: eap-cd-0
         podIP: 10.131.0.246
         state: ACTIVE
     replicas: 1
     scalingdownPods: 0