Internal .Net Framework Data Provider Error 1.

VS2k5   
Win2k3
IIS6
.NET 2.0

In my ASP.NET 2.0 app I create and open an SQL connection in the page's constructor and call Dispose() in the destructor.  The SQLConnection
object is a class member of the page.  This page makes heavy use of the SQLConnection object so I felt opening and closing in the constructor/destructor respectively was good design.  I know this doesn't take full advantage of connection pooling.  Any design input would be very much appreciated.


Here's the destructor code:

/// Destructor
~Officer()
{
    if( m_objConn != null )
        m_objConn.Dispose(); // <-- Exception occurrs here.
}
/// End Destructor


When running this particular page through some testing I get the following exception in the destructor at the "m_objConn.Dispose();" line:

System.InvalidOperationException was unhandled
  Message="Internal .Net Framework Data Provider error 1."
  Source="System.Data"
  StackTrace:
       at System.Data.ProviderBase.DbConnectionInternal.PrePush(Object expectedOwner)
       at System.Data.ProviderBase.DbConnectionPool.PutObject(DbConnectionInternal obj, Object owningObject)
       at System.Data.ProviderBase.DbConnectionInternal.CloseConnection(DbConnection owningObject, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Close()
       at System.Data.SqlClient.SqlConnection.Dispose(Boolean disposing)
       at System.ComponentModel.Component.Dispose()
       at Officer.Finalize() in c:sysprojectsAddOfficer.aspx.cs:line 46

1)  Is this design good/bad?
1)  Is this a bug?
2)  Do I need a try/catch in a destructor?  Is it good programming practice?
3)  Why is this happening?
4)  What is the meaning of life?

Any help is appreciated.  TIA