user1983: After a contract has fulfilled its mission in life (such as pay beneficiary), is it proper to delete or disable said contract? If so, how exactly is this done?
Offhand, I would think that if the contract gets needlessly validated (for the rest of eternity [yikes!]) it would needlessly clog up the system.

user1130: 
I would think that if the contract gets needlessly validated (for the rest of eternity [yikes!])

Ah. This is a misunderstanding. Scripts are completely passive. Nothing gets run unless a transaction interacts with it.
So, in the case of a contract that pays a beneficiary, the script doesn't do that for you, it includes a validator that says "yes" or "no" to anyone trying to spend the UTxOs at the script address.

user2300: I don't think "disabling" a contract is possible since a "contract" in Cardano is not deployed anywhere on chain. The script/contract is supplied with a transaction that wants to spend UTXOs sitting at the contract address (which is basically a hash of the script code). Anybody can construct such at transaction at any time and the validator node will need to validate it.
The network will not be congested because as others have pointed out "contracts" in Cardano are completely passive and do not run on their own. They only run if a transaction wants to spend UTXOs sitting at the script address. If somebody would want to attack the network and construct millions of such transactions to run the code it would ruin him because each transaction has to pay fees and the fees are based on the resources needed to run the script. The more computational/memory heavy the script is the more fees you have to pay.

1983: <p>After a contract has fulfilled its mission in life (such as pay beneficiary), is it proper to delete or disable said contract? If so, how exactly is this done?</p>
<p>Offhand, I would think that if the contract gets needlessly validated (for the rest of eternity [yikes!]) it would needlessly clog up the system.</p>
 1130: <blockquote>
<p>I would think that if the contract gets needlessly validated (for the rest of eternity [yikes!])</p>
</blockquote>
<p>Ah. This is a misunderstanding. <em>Scripts are completely passive.</em> Nothing gets run unless a transaction interacts with it.</p>
<p>So, in the case of a contract that pays a beneficiary, the script doesn't do that for you, it includes a validator that says &quot;yes&quot; or &quot;no&quot; to anyone trying to spend the UTxOs at the script address.</p>
 2300: <p>I don't think &quot;disabling&quot; a contract is possible since a &quot;contract&quot; in Cardano is not deployed anywhere on chain. The script/contract is supplied with a transaction that wants to spend UTXOs sitting at the contract address (which is basically a hash of the script code). Anybody can construct such at transaction at any time and the validator node will need to validate it.</p>
<p>The network will not be congested because as others have pointed out &quot;contracts&quot; in Cardano are completely passive and do not run on their own. They only run if a transaction wants to spend UTXOs sitting at the script address. If somebody would want to attack the network and construct millions of such transactions to run the code it would ruin him because each transaction has to pay fees and the fees are based on the resources needed to run the script. The more computational/memory heavy the script is the more fees you have to pay.</p>
