Hermes triggers Websocket related error messages in full node logs

[mpoke]

Summary of Bug

While going through the Hermes tutorial, running any hermes command results in error messages in the log of the chains:

$ hermes tx raw create-client ibc-1 ibc-0
    Finished release [optimized] target(s) in 0.20s
     Running `target/release/hermes tx raw create-client ibc-1 ibc-0`
2021-11-04T16:46:52.557761Z  INFO ThreadId(01) using default configuration from '~/.hermes/config.toml'
2021-11-04T16:46:52.574469Z  WARN ThreadId(21) [ibc-1] waiting for commit of tx hashes(s) 15F2B514FFFC4A1F160E17E18BE8766A7331EB0304DD5ADFB3A8049BA65EB805
Success: CreateClient(
    CreateClient(
        Attributes {
            height: Height {
                revision: 1,
                height: 1079,
            },
            client_id: ClientId(
                "07-tendermint-0",
            ),
            client_type: Tendermint,
            consensus_height: Height {
                revision: 0,
                height: 1091,
            },
        },
    ),
)

$ tail -f ./data/ibc-0.log
5:46PM ERR Failed to read request err="websocket: close 1006 (abnormal closure): unexpected EOF" module=rpc-server protocol=websocket remote={"IP":"127.0.0.1","Port":58344,"Zone":""}
5:46PM ERR error while stopping connection error="already stopped" module=rpc-server protocol=websocket

Version

v0.8.0

Steps to Reproduce

Acceptance Criteria

---

For Admin Use

• [ ] Not duplicate issue
• [ ] Appropriate labels applied
• [ ] Appropriate milestone (priority) applied
• [ ] Appropriate contributors tagged
• [ ] Contributor assigned/self-assigned